This repository was archived by the owner on Jul 6, 2022. It is now read-only.
docs(jwt): update options config of jwt (#87)
#164
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/docs/3upWGHLeVRudNiqEhFoGPj2qAbiw |
0ubbe
commented
Dec 8, 2021
0ubbe
commented
Dec 8, 2021
0ubbe
commented
Dec 8, 2021
balazsorban44
approved these changes
Dec 8, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes 💡
Following out update of
josenextauthjs/next-auth#3039, the way to configurejwtchanged. These are the options changes I inferred from the PR:export default NextAuth({ // ... jwt: { secret, maxAge, - encryptionKey - signingKey - encryptionKey - verificationOptions encode({ token secret maxAge - signingKey - signingOptions - encryptionKey - encryptionOptions - encryption }) {}, decode({ token secret - maxAge - signingKey - verificationKey - verificationOptions - encryptionKey - decryptionKey - decryptionOptions - encryption }) {} } })I updated the relevant docs I could find mentioning
jwtconfig in v4. I lack a bit of context for this 🎻Affected issues 🎟
#87
Screenshot (If Applicable) 📷
–